home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19990725-20000114
/
000201_news@columbia.edu _Fri Oct 15 12:26:06 1999.msg
< prev
next >
Wrap
Internet Message Format
|
2000-01-13
|
2KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id MAA24248
for <kermit.misc@watsun.cc.columbia.edu>; Fri, 15 Oct 1999 12:26:05 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id MAA01342
for kermit.misc@watsun.cc.columbia.edu; Fri, 15 Oct 1999 12:04:58 -0400 (EDT)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Subject: Re: Capturing output to file from script (UNIX)
Date: 15 Oct 1999 16:04:58 GMT
Organization: Columbia University
Message-ID: <7u7jba$19r$1@newsmaster.cc.columbia.edu>
To: kermit.misc@columbia.edu
In article <38074E30.2DBED3DB@concentric.net>,
Jay Weinshenker <jweinshe@concentric.net> wrote:
: I'm running C-Kermit 6.0.192, 6 Sep 96, for Solaris 2.x and
: configuring it to run a script and that's it. In this script, I've got
: everything going well, except that at one point it downloads a file.
:
: Now, the server I am connecting to prompts for a filename and upon my
: script passing a filename and a carriage return, the server spews the
: file to the screen (which is ok). I'm having a DEVIL of a time getting
: my kermit client to capture this output to a file - I've tried set
: session-log binary, set session-log text, and also set printer
: <filename> and I can't seem to get any of them to work - I *know* this
: is possible...
:
: Can someone help me with this?
:
Let's suppose it's a text file, since it usually doesn't make sense to
spew a binary file to the screen. Then all it should take is:
log session capture.log
output <filename>\13
input 200 <xxx>
if fail echo WARNING: INPUT timed out after 200 seconds
close session
where <xxx> is what the server prints when it's finished spewing the file,
and let's hope it's not in the file itself. The result should be in the
capture.log file.
Or is this an HTTP GET? In that case there might be a better way.
- Frank